Resource Management System, Resource Information Providing Method and Program

ABSTRACT

To provide a resource management system capable of stably providing most recently updated resource information at a high speed. A resource information update unit collects resource information from a plurality of agents by means of agent connection management unit according to an update schedule of resource information stored in a schedule storage unit, and stores the same in a resource information storage unit. A retrieval processing unit accesses the resource information storage unit to acquire retrieval results of resource information. A static schedule generation unit selects update interval for each of resource information, generates a static schedule, and store the same in the schedule storage unit.

TECHNICAL FIELD

The present invention relates to a resource management system, aresource information providing method and a program. More particularly,the present invention relates to a resource management system, aresource information providing method and a program for providingresource information in a distributed information system.

BACKGROUND ART

Conventional resource information management systems for clusters canexecute processes for collecting information from all the nodes stablyat a high speed because the nodes have a uniform performance and areconnected to one another by way of a high speed network. However, in thecase of a system for consolidating and managing a plurality of clustersconnected by way of a wide area network or a plurality of personalcomputers of different types, it is time consuming to acquire resourceinformation particularly when the scope of retrieval of resourceinformation is large and the processing time may vary depending on theobject of retrieval.

An MDS (monitoring discovery system) described in Non-Patent Publication1 is known as resource information management system in a wide areadistributed system. An MDS manages resource information by means of adirectory and, when a retrieval process takes place for resourceinformation, it acquires the required resource information and cachesthe same in the directory. When another retrieval process takes placefor the same resource information, the cached resource information canbe provided to the new retrieving party to reduce the retrieving time.The effective period of the cache is defined in advance for the resourceinformation collected by the MDS. When a client requests for informationafter the expiration of the effective period, the cached information isdestroyed and a process for acquiring the most recently updatedinformation is executed. A plurality of MDSs can be linked to oneanother in a hierarchical manner. Thus, a variety of different systemscan be realized by using MDSs to cover a single cluster and large scaledistributed systems.

Patent Publication 1 describes a technique wherein a data updatingmethod uses a network server. With the described technique, thefrequency of access to the data held in a cache by client terminals isdetected and the data is read out from a main server before the holdingperiod of the cache expires to update the data held in the cache. Withthis arrangement, it is possible to automatically update the cache datathat can be expected to be accessed by client terminals in the future,whereby the most recently updated data can be transferred to a clientterminal in a short time.

Patent Publication 1: JP-2001-175527-A (FIG. 1, Summary)

Non-Patent Document 1: Grid Information Services for Distributedresource Sharing, Czajkowski, K.; Fitzgerald, S.; Foster, I.; Kesselman,C.; High Performance Distributed Computing, 2001. Proceedings, 10th IEEEInternational Symposium on, 7-9 Aug. 2001

DISCLOSURE OF THE INVENTION Problems to be Solved by the Invention

Both the resource information updating system using MDSs and the dataupdating method of the Patent Publication 1 involve the problem that,when the effective period of the cache has expired, the information usedto be held in the cache needs to be collected anew and hence it takes along time to retrieve the information. Additionally, when there is arequest for information that has not been retrieved so far, theinformation is not found in the cache and hence it takes a long time toretrieve the information. Further, while the information can be acquiredat a high speed from the cache within the effective period thereof, thetime length required to retrieve the information may vary depending onthe state of the cache even if the retrieval process is executed underthe same condition, whereby there arises the problem that the retrievaltime is not stable.

Therefore, it is an object of the present invention to provide aresource management system, a resource information providing system anda program that can dissolve the problems of the conventional techniqueand provide the most recently updated resource information stably at ahigh speed.

Means for Solving the Problems

The present invention provides, in a first aspect thereof, a resourcemanagement system including a resource information providing server forproviding resource information relating to a plurality of resourcesconnected to a network in response to a request from a resource user,characterized in that the resource information providing serverincludes: a resource information storage unit storing therein resourceinformation; a schedule storage unit storing therein an updatingschedule of the resource information stored in the resource informationstorage unit; and a resource information update unit for acquiring theresource information based on the schedule stored in the schedulestorage unit, and updating the resource information stored in theresource information storage unit by the acquired resource information,and that the schedule storage unit stores therein at least an updatingschedule having an updating interval defined for each resource for whichresource information is to be acquired.

With the resource management system in the first aspect of the presentinvention, the resource information stored in the resource informationstorage unit is updated based on the updating schedule and each resourceuser is provided with resource information from the resource informationmemory device. Therefore, it is not necessary to acquire resourceinformation each time a request is received from a resource user,whereby the resource user can be provided with resource information at ahigh speed. Additionally, since the resource information stored in theresource information storage unit is updated based on the updatingschedule at an updating interval defined for each resource, it ispossible to update the resource information of each resource based onthe characteristics of the resource.

The present invention provides, in a second aspect thereof, a resourcemanagement system including a resource information providing server forproviding resource information relating to a plurality of resourcesconnected to a network in response to a request from a resource user,characterized in that the resource information providing serverincludes: a resource information storage unit storing resourceinformation; a schedule storage unit storing an updating schedule of theresource information stored in the resource information storage unit; aresource information update unit for acquiring the resource informationaccording to the schedule stored in the schedule storage unit andupdating the resource information stored in the resource informationstorage unit by the acquired resource information; and a dynamicschedule generation unit for dynamically modifying the updating schedulestored in the schedule storage unit based on at least one of a state ofthe resources, a state of the resource information providing server anda state of the communication line.

With the resource management system in the second aspect of the presentinvention, the resource information stored in the resource informationstorage unit is updated based on the updating schedule and each resourceuser is provided with resource information from the resource informationmemory device. Therefore, it is not necessary to acquire resourceinformation each time a request is received from a resource user,whereby the resource user can be provided with resource information at ahigh speed. Additionally, as the dynamic schedule generation unitdynamically modifies (alters) the updating schedule typically based onthe change in the state of each resource and quickly updates theresource information that has changed, whereby the resource user can beprovided with the most recently updated resource information.

The present invention provides, in a third aspect thereof, a method forproviding resource information by means of a resource informationproviding server for providing resource information relating to aplurality of resources connected to a network, in response to a requestfrom a resource user, characterized by the steps of: storing in aschedule storage unit an updating schedule defining an updating timingof resource information and including an updating interval selected atleast for each resource for which resource information is to beacquired; acquiring resource information based on the updating schedulestored in the schedule storage unit and storing the acquired resourceinformation in a resource information storage unit; and providing theresource information stored in the resource information storage unit inresponse to a request from a resource information user.

The present invention provides, in a fourth aspect thereof, a programrunning on a resource information providing server for providingresource information relating to a plurality of resources connected to anetwork, in response to a request from a resource user, the programallowing the resource information providing server to execute theprocessings of: storing in a schedule storage unit an updating scheduledefining an updating timing of resource information and including anupdating interval selected at least for each resource for which resourceinformation is to be acquired; acquiring resource information based onthe updating schedule stored in the schedule storage unit and storingthe acquired resource information in a resource information storageunit; and providing the resource information stored in the resourceinformation storage unit in response to a request from a resourceinformation user.

With the resource information providing method in the third aspect ofthe present invention and a program in the fourth aspect of the presentinvention, the resource information stored in the resource informationmemory device is updated based on the updating schedule and eachresource user is provided with resource information from the resourceinformation memory device. Therefore, it is not necessary to acquireresource information each time a request is received from a resourceuser, whereby the resource user can be provided with resourceinformation at a high speed. Additionally, since the resourceinformation stored in the resource information memory device is updatedbased on the updating schedule at an updating interval defined for eachtype (category) of the resources, it is possible to update the resourceinformation of each resource based on the characteristics of resource.

The present invention provides, in a fifth aspect thereof, a method forproviding resource information by means of a resource informationproviding server for providing resource information relating to aplurality of resources connected to a network in response to a requestfrom a resource user, characterized by the steps of: storing an updatingschedule defining the updating timing of resource information in aschedule storage unit; acquiring resource information according to theupdating schedule stored in the schedule storage unit and storing theacquired resource information in a resource information storage unit;dynamically modifying the updating schedule stored in the schedulestorage unit based on at least one of a state of the resources, a stateof the resource information providing server and a state of acommunication line; and providing the resource information stored in theresource information storage unit in response to a request from aresource information user.

The present invention provides, in a sixth aspect thereof, a programrunning on a resource information providing server for providingresource information relating to a plurality of resources connected to anetwork, in response to a request from a resource user, the programallowing the resource information providing server to execute theprocessings of: storing an updating schedule defining the updatingtiming of resource information in a schedule storage unit; acquiringresource information according to the updating schedule stored in theschedule storage unit and storing the acquired resource information in aresource information storage unit; dynamically modifying the updatingschedule stored in the schedule storage unit based on at least one of astate of the resources, a state of the resource information providingserver and a state of a communication line; and providing the resourceinformation stored in the resource information storage unit in responseto a request from a resource information user.

With the resource information providing method in the fifth aspect ofthe present invention and a program in the sixth aspect of the presentinvention, the resource information stored in the resource informationmemory device is updated based on the updating schedule and eachresource user is provided with resource information from the resourceinformation memory device. Therefore, it is not necessary to acquireresource information each time a request is received from a resourceuser, whereby the resource user can be provided with resourceinformation at a high speed. Additionally, as the resource informationupdating schedule is dynamically modified, the resource user can beprovided with the most recently updated resource information typicallyby dynamically modifying (altering) the updating schedule based on thechange in the state of each resource so as to quickly update theresource information that has changed.

ADVANTAGES OF THE INVENTION

With the resource management system, the resource information providingmethod and the program according to the present invention, the resourceinformation stored in the resource information memory device is updatedbased on the updating schedule and each resource user is provided withresource information from the resource information memory device.Therefore, it is not necessary to acquire resource information each timea request is received from a resource user, and the resource user can beprovided with resource information afresh and at a high speed.Additionally, the time length required to provide resource informationis made uniform to stabilize the resource retrieval.

BEST MODE FOR CARRYING OUT THE INVENTION

With the resource management system in the first aspect of the presentinvention, it is preferable that the different types of resources havedifferent updating time intervals. Then, the updating intervals can bedefined with ease.

In another preferable embodiment, the resource information providingserver further includes a static schedule generation unit for generatingthe updating schedule based on at least one of the pieces of informationincluding the performance of the resource information providing server,the expected frequency of updating resource information, the expectedfrequency of request for resource information from resource users, theupdating time expected to be required to update each piece of resourceinformation and the number of resources and storing the updatingschedule in the schedule storage unit. With such an arrangement, theupdating process can be adapted to the performance of the server, thecharacteristics of resources and so on.

In the resource management system in the first aspect of the presentinvention, the resource information providing server preferably furtherincludes a dynamic schedule generation unit for dynamically modifyingthe updating schedule stored in the schedule storage unit based on atleast one of the state of the resources, the state of the resourceinformation providing server or the state of the communication line.With such an arrangement, it is possible to provide resource users withthe most recently updated resource information by dynamically modifying(altering) the updating schedule so as to quickly update the resourceinformation that has changed based on the change in the state of theresources.

In the resource management system according to the invention, thedynamic schedule generation unit can modify the updating schedulecorresponding to the increase or decrease of the number of resources.With such an arrangement, it is possible to realize an updating processbased on the number of resources.

In the resource management system according to the present invention,when a request for resource information is produced by a resource user,the dynamic schedule generation unit preferably shortens the updatinginterval of the resource information for which the request is produced.With such an arrangement, it is possible to provide the most recentlyupdated resource information by shortening the updating interval of theresource information for which requests are frequently produced.

In the resource management system according to the present invention,when a trouble arises to any of the resources or the communication line,the updating interval of the resource information relating to thetrouble are preferably shortened. With such an arrangement, it ispossible to provide the most recently updated resource information thatis required to cope with the trouble accurately and quickly.

In the resource management system according to the present invention,when the configuration of a resource is altered, the dynamic schedulegeneration unit preferably shortens the updating interval of theresource information of the altered resource. With such an arrangement,it is possible to update the resource information stored in the resourceinformation storage unit with the most recently updated resourceinformation.

In the resource management system according to the present invention,the dynamic schedule generation unit preferably prolongs the updatinginterval of the resource information that has not altered by the pastupdates of resource information. With such an arrangement, it ispossible to reduce the load of the process of updating resourceinformation by prolonging the updating interval of the resourceinformation that has not been changed to a large extent.

In the resource management system according to the present invention,the dynamic schedule generation unit preferably prolongs the updatinginterval of resource information in general when the load of theresource information providing server or the communication line rises.With such an arrangement, it is possible to reduce the load of theresource information providing server or the communication line byreducing the load of the resource information updating process.

The resource management system according to the present invention mayfurther include an agent for collecting resource information from theresources, the agent being adapted to transmit resource information tothe resource information update unit. It is possible for the resourceinformation providing server to collect resource information by way ofthe agent.

In the resource information management system according to the presentinvention, the agent may register an automatic notification request thatspecifies notification conditions and resource information. When thenotification conditions specified by the automatic notification requestarise, the agent transmits the resource information specified by theautomatic notification request to the resource information update unit.With this arrangement, it is possible to update the resource informationwithout accessing the agent from the resource information providingserver by causing the agent to notify the resource information, wherebythe load of processing can be reduced. Then, the resource informationproviding server can know the time when it receives a notification fromthe agent, by specifying a time zone for receiving notifications fromthe agent as notification condition.

In the resource information management system according to the presentinvention, the updating schedule may specify the resource information tobe acquired at each of the pollyings that the resource informationupdate unit carries out at a predetermined time interval. Then, theresource information update unit acquires the resource informationspecified so as to be acquired and updates the resource informationstored in the resource information storage unit.

In the resource information management system according to the presentinvention, it may be possible to define the upper limit of the resourceinformation to be acquired at each polling based on the memory capacityof the resource information providing server. Then, it is possible toprevent the load of the resource providing server or the communicationline from excessively rising by suppressing the resource information tobe acquired when the updating schedule is generated so as not to exceedthe defined upper limit.

Now, embodiments of the present invention will be described in greaterdetail by referring to the accompanying drawings. FIG. 1 shows aresource management system according to a first embodiment of thepresent invention. The resource management system 100 includes aplurality of resource user terminals 1, a plurality of resourceproviding servers 2 and a plurality of agents 3. The resource managementsystem 100 is realized as a system that can consolidate, run and managethe resources of the system to be managed including servers, networksand applications.

The resource user terminals 1 and the resource providing servers 2operate on a computer system, which may typically be a work station etc.The resource providing servers 2 are typically realized as, for example,data centers for providing execution environments (resources) ofapplications and actually provide the resource user terminals 1 with anexecution environment. The agents 3 operate on software and hardwarethat can acquire resource information. The agents 3 typically acquiresetting information of network equipment and assigned band informationof applications as resource information 31. The resource providingservers 2 communicate with a plurality of agents 3 to collect resourceinformation that the agents 3 acquire.

Each of the resource user terminals 1 includes a monitor component 11,an autonomous control component 12 and a resource selection component13. The monitor component 11 transmits a resource information retrievalrequest to the resource providing servers 2 to acquire resourceinformation. The monitor component 11 monitors the state of theresources based on the resource information thus acquired, and generatesa predetermined event based on the state of each of the resources itmonitors. The monitor component 11 typically acquires a load informationof each of the resource providing servers 2 and, when the load of arecording providing server 2 exceeds a threshold value, it issues anevent that indicates the excess.

The monitor component 11 delivers the event it generates into theautonomous control component 12. The autonomous control component 12stores therein the corresponding relationship between an event and anaction to be started for the event as a control policy. The autonomouscontrol component 12 determines the action to be started based on theinput from the monitor component 11, referring to the control policy,and delivers an execution request of the action to the resourceselection component 13. The autonomous control component 12 typicallyreceives as input an event indicating that the load of the serverresource that the resource user terminal 1 is using exceeds thethreshold value and delivers an action execution request forsupplementing the server resource to the resource selection component13.

The resource selection component 13 provides a resource selectionfunction when an action is to be executed. Whenever necessary, theresource selection component 13 acquires resource information from theresource providing servers 2 via the monitor component 11 and determinesa resource providing server 2 to which an action execution request is tobe forwarded based on the acquired resource information. When an actionexecution request for supplementing a server resource is input, theresource selection component 13 typically acquires resource informationfrom a plurality of resource providing servers 2, retrieves a resourceproviding server 2 holding a resource that can be supplied as supplementand transmits an action execution request for supplying the resource assupplement to the resource providing server 2 holding the resource thatcan be supplied as supplement.

Each of the resource providing servers 2 includes a resource informationretrieval component 21, a resource management component 22 and aworkflow management component 23. The resource management component 22manages accesses to the agents 3 that are objects of management. Theresource management component 22 communicates with a plurality of agents3 that are objects of management to collect and hold resourceinformation 31. The resource information retrieval component 21 receivesa request for a resource information retrieval process from any of theresource user terminals 1, acquires resource information from theresource management component 22 and forwards back the acquired resourceinformation to the resource user terminal 1.

The workflow management component 23 receives the action executionrequest from the resource user terminal 1 and generates a detailedworkflow based on the action execution request. Whenever necessary atthis time, the workflow management component 23 transmits a resourceinformation retrieval request to the resource information retrievalcomponent 21 and acquires resource information. The agent 3 has thefunctions of executing a command, writing the property file of anapplication, managing the state of assignment and so on. The workflowgenerated by the workflow management component 23 is transmitted to theagent 3 by way of the resource management component 22 and executed bythe agent 3.

FIG. 2 shows the detailed configuration of the resource managementcomponent 22 and agents 3. Each agent 3 includes a manager connectionunit 301 and a resource information acquisition unit 302. The managerconnection unit 301 manages the connection between the agent 3 and theresource management component 22. The resource information acquisitionunit 302 acquires resource information 31 from the object of management.

The resource management component 22 includes a retrieval processingunit 221, a resource information storage unit 222, a resourceinformation update unit (cash update unit) 223, a static schedulegeneration unit 224, a schedule storage unit 223, an agent connectionmanagement unit 226 and a workflow execution unit 227. The agentconnection management unit 226 communicates with the agent 3. Theworkflow execution unit 227 receives the workflow generated by theworkflow management component 23 as input and operates the agent 3 basedon the workflow so as to execute the workflow by way of the agentconnection management unit 226.

The static schedule generation unit 224 generates a resource informationupdating schedule (cache updating schedule) and stores the same in theschedule storage unit 225. The manager may directly operate the updatingschedule stored in the schedule storage unit 225 by way of an input unit4. The resource information update unit 223 acquires resourceinformation 31 from the agent 3 by way of the agent connectionmanagement unit 226 based on the updating schedule stored in theschedule storage unit 225 and stores the same in the resourceinformation storage unit (cache) 222.

The resource information update unit 223 acquires resource information31 from the agent 3 by means of a polling, for example, that is repeatedat the predetermined time interval. The schedule storage unit 225 storesthe timetable that specifies the resource information to be updated ateach polling and the resource information update unit 223 acquires thespecified resource information based on the timetable and updates theresource information stored in the resource information storage unit222. The retrieval processing unit 221 retrieves the resource from theinside of the resource information storage unit 222 based on the requestfrom the resource information retrieval component 21 and forwards backthe requested resource information to the resource information retrievalcomponent 21.

Upon generating a static schedule, the static schedule generation unit224 refers to the performance information of the computer system thatrealizes the resource management component 22 and other information(parameters) including the frequency of updating the resourceinformation, the time length required to update the resourceinformation, the application of the resource information, theperformance of the server and the network and the number of the objectsof management. Then, the static schedule generation unit 224 generates astatic schedule that can realize a cache updating process that matchesthe system performance, while satisfying the request of the user.

Upon generating a static schedule, the static schedule generation unit224 appropriately selects the number of simultaneous accesses of agentsand updating the interval so as not to give rise to an excessive load tothe servers and the network. For example, when agents accesses tens ofseveral server hosts, it limits the number of simultaneous accesses ofagents and shifts the timings of accesses of agents by several secondsin order to prevent the load of the computers and the network from beingraised excessively. Additionally, it prolongs the updating interval ofeach resource to prevent accesses of agents from taking place toofrequently when there are a large number of pieces of resourceinformation as the objects of management.

The static schedule generation unit 224 has rules for determining thepolling intervals and the number of simultaneous accesses of agentsbased on the CPU performance and the memory capacity in the memorydevice. The static schedule generation unit 224 acquires information onthe CPU performance and the memory capacity of the computer system thatrealizes the resource management component 22 and determines the pollinginterval and the number of simultaneous accesses of agents based on therules stored in the memory device. The resource information update unit223 operates for pollyings at the determined time interval.

The static schedule generation unit 224 selects a smaller pollinginterval when the CPU clock operates at a high speed and a large numberof simultaneous accesses of agents when the memory capacity is large.For example, the static schedule generation unit may select a second forpolling interval when the CPU clock is 2 GHz or higher and 15 for thenumber of simultaneous accesses of agents when the memory capacity is 1GB or greater.

The static schedule generation unit 224 selects the frequency ofupdating each piece of resource information based on the characteristicsof the corresponding resource. For example, the static schedulegeneration unit 224 selects a shorter updating interval for the CPUutilization ratio, the memory utilization ratio and so on that need tobe updated more frequently, compared with the configuration informationand selection information that may be updated less frequently. It alsoselects a longer updating interval for resource information thatrequires a longer acquisition time length.

Priority may be defined for each piece of resource information. Thestatic schedule generation unit 224 updates more frequently pieces ofresource information having a higher priority than pieces of resourceinformation having a lower priority. Upon defining the priority, thestatic schedule generation unit 224 provides a higher priority to piecesof resource information that are requested more frequently by users sothat those pieces of resource information may be updated with a higherpriority. Again, a relatively long interval will be selected to updatepieces of resource information that only few users request to be updatedfrequently.

FIG. 3 illustrates the algorithm for the generation of the staticschedule by the static schedule generation unit 224. In the following,three categories of resource information including the category ofserver hosts, that of network equipment and that of assigned bands willbe discussed. Additionally, it is assumed that the polling interval ofthe resource information update unit 223 is one second and the number ofsimultaneous accesses of agents (maximum value) is 7. The staticschedule generation unit 224 has a resource profile that stores theapproximate time length necessary for acquiring resource information andthe initial value of the resource information updating interval for eachresource category. A plurality of resource profiles may be provideddepending on the network bandwidth. As the manager specifies resourcecategories and registers resource information by way of the input unit4, the static schedule generation unit 224 selects an updating intervalfor each category of resource information, referring to the relatedresource profile (Step A1).

Assume here that the static schedule generation unit 224 has a resourceprofile as shown in FIG. 4. The resource profile defines the updatinginterval for the case of the network bandwidth being 100 B/s, forexample. In this case, if Host01 through Host08 are registered as serverhosts, the static schedule generation unit 224 selects 3 seconds for theupdating interval of resource information of each server host. Inaddition, if L2SW (layer 2 switch), L3SW (layer 3 switch), FW(firewall), PS (packet shaper) and LB (load balancer) are registered asnetwork equipment, the static schedule generation unit 224 selects 8seconds for the updating interval of the resource information of thenetwork equipment. Similarly, as band information of AP1 and that of AP2are registered as information of assigned bands for applications, thestatic schedule generation unit 224 selects 5 seconds for the updatinginterval of the band information of those applications.

The static schedule generation unit 224 divides the number ofsimultaneous accesses of agents based on the number of pieces ofresource information belonging to the categorized resources (Step A2)and selects the number of simultaneous accesses of agents for eachcategory. For example, the static schedule generation unit 224 mayselect 4 as the number of simultaneous accesses of agents for serverhosts, 2 as the number of simultaneous accesses of agents for networkequipment and 1 as the number of simultaneous accesses of agents forband information of applications.

The static schedule generation unit 224 determines whether or not anupdating schedule is generated for all the categories (Step A3) and, ifthere is at least an unprocessed category, it further executes a processof preparing an updating schedule for each category. In the process ofpreparing an updating schedule for each category, the static schedulegeneration unit 224 firstly sorts pieces of resource information basedon the priorities assigned to the respective categories of resourceinformation (Step A4). Then, the static schedule generation unit 224assigns priorities to the categories of resource information in thedescending order of priorities based on the updating interval selectedin Step A1 (Step A5). When it is determined that an updating schedule isprepared for all the categories, the process comes to an end.

FIG. 5 exemplifies the static schedule generated by the static schedulegeneration unit 224. In FIG. 5, the abscissa indicates the time lengthelapsed since the current clock time so as to correspond to pollyings.In addition, each shaded area shows that the resource information isspecified so as to be updated at the corresponding poll.

The static schedule generation unit 224 determines the timing in thedefault updating interval of the pieces of resource information of eachcategory and generates an updating pattern for the updating interval inStep A5. At this step, the static schedule generation unit 224 soregulates the updating timing of each piece of resource information thatthe number of simultaneous accesses of agents defined in Step A2 foreach category may not be exceeded. For example, as for the category ofhost servers, the static schedule generation unit 224 determines thetiming in the updating interval (3 seconds) of each of the pieces ofresource information belonging to the category and generates an updatingpattern for the updating period of 3 seconds. Thereafter, the staticschedule generation unit 224 arranges the generated updating patternrepeatedly to generate an updating schedule as shown in FIG. 5.

FIG. 6 shows operation of the cache updating process in a flowchart. Theresource information update unit 223 acquires the list of pieces ofresource information to be updated at the current polling (1 secondafter the timetable of FIG. 5) from the schedule storage unit 225 (StepB1), and confirms the pieces of resource information for which the cacheneeds to be updated. The resource information update unit 223 generatesan agent access request necessary for the cache updating process basedon the list it acquires in Step B1 (Step B2), and delivers the generatedagent access request to the agent connection management unit 226. Uponreceiving the agent access request, the agent connection management unit226 communicates with the agent 3 to be updated and executes the processfor acquiring resource information (Step B3). The agent connectionmanagement unit 226 acquires the most recently updated resourceinformation 31 from the agent 3 (Step B4), and stores the acquiredresource information 31 in the resource information storage unit 222(Step B5).

For example, if the schedule storage unit 225 stores therein thetimetable as illustrated in FIG. 5, the resource information update unit223 acquires “Host01”, “Host04”, “L2SW”, “PS” and “AP1” from theschedule storage unit 225 in Step B1, and confirms that the resourceinformation to be updated this time includes the setting information forHost01, Host04, L2S and PS and assigned band information of applicationAP1. Subsequently, the resource information update unit 223 generates anaccess request to the agent 3 from which the resource information to beupdated is to be acquired. As a result, the resource information of theresource specified in the updating schedule is updated out of the piecesof resource information of resources stored in the resource informationstorage unit 222.

FIG. 7 shows the operation of executing the resource informationretrieval requesting process in a flowchart. If the resource userterminal 1 delivers a retrieval request in a resource providing server2, the retrieval processing unit 221 receives the retrieval request byway of the resource information retrieval component 21 (Step C1). Theretrieval processing unit 221 executes pre-retrieval processes includinga process of creating an inquiry for accessing the resource informationstorage unit 222 and a process of checking the limit of accesses (StepC2), and acquires resource information from the resource informationstorage unit 222 (Step C3). Thereafter, the retrieval processing unit221 executes post-retrieval processes including a format conversionprocess for results information and a process of adding additionalinformation (Step C4), and forwards back the outcome of the retrieval tothe resource user terminal 1 that generated the retrieval request (StepC5).

FIG. 8 shows the operation of the resource management system in aflowchart. The autonomous control component 12 specifies the resourceinformation to be monitored to the monitor component 11. The monitorcomponent 11 periodically generates a retrieval process for retrievingresource information of the resource to be monitored that is specifiedby the autonomous control component 12, and following the sequenceillustrated in FIG. 7, acquires the resource information to be retrievedto monitor the state of the resource (Step D1). The monitor component 11includes a memory device for storing therein conditions of eventgeneration, and determines whether or not an event is to be generatedbased on the acquired resource information, by referring to the memorydevice (Step D2).

The monitor component 11 issues an event when it determines that theresource information acquired in Step D1 meets the conditions of eventgeneration, and notifies the autonomous control component 12 of thegeneration of the event. Events that the monitor component 11 generatesinclude load change events, obstacle generation events and timerstarting events. The monitor component 11 returns to Step D1 withoutgenerating an event and regains the monitoring state when it determinesthat the resource information acquired in Step D1 does not meet theconditions of event generation.

The autonomous control component 12 stores therein the control policythat describes the action to be taken for the notified event. The actionto be started includes, for example, addition of a host, alteration ofnetwork band assignment and notification of application load. Uponreceiving notification of the generated event, the autonomous controlcomponent 12 retrieves the control policy (Step D3), and determineswhether or not the action for the notified event is described in thecontrol policy (Step D4). If it is determined in Step D4 that the actionfor the notified event is not described in the control policy, theautonomous control component 12 returns to Step D1 and regains themonitoring state. If it is determined in Step D4 that the action for thenotified event is described in the control policy, the autonomouscontrol component 12 generates an action execution request based on thecontrol policy and delivers the request to the resource selectioncomponent 13 (Step D5).

The resource selection component 13 retrieves the resource informationand selects the resource by way of the monitor component 11 based on theinput action execution request (Step D6), and determines whether or notthe requested action can be processed in the current environment (StepD7). The resource selection component 13 retrieves idle servers andselects one of the resource providing servers 2 having an idle server inresponse to a request for adding a server resource, for instance. Ifthere is not any resource providing server 2 having an idle server, theresource selection component 11 determines that it is not possible toexecute the requested action.

If the resource selection component 13 determines in Step D7 that therequested action cannot be taken, it notifies the manager of the factthat it failed in taking the action (Step D8), and returns to Step D1 toregain the monitoring state. If the resource selection component 13determines in Step D7 that the requested action can be taken, ittransmits an action execution request to the resource providing server 2selected in Step D6.

The resource providing server 2 receives the action execution request byway of the workflow management component 23. The workflow managementcomponent 23 associates the action execution request with the workflowthat is to be generated in response to the execution request and, storesthe same in a memory device (not shown). The workflow managementcomponent 23 refers to the memory device and generates a detailedworkflow according to the received action execution request (Step D9).

When, for example, the workflow management component 23 receives anaction execution request for adding the object server to an loadbalancer, it directs the resource information retrieval component 21 toretrieve the setting information of the current load balancer at thetime of generating the workflow in Step D9, and acquires the settinginformation. Thereafter, in Step D9, it generates a setting where theobject server to be added is actually added to the current setting, andalso generates a workflow for allowing the load balancer to alter thesetting.

The workflow management component 23 transmits the generated workflow tothe workflow execution unit 227 and requests the latter to execute theworkflow (Step D10). The workflow execution unit 227 operates the agent3 by way of the agent connection management unit 226 based on thereceived workflow (Step D11) to execute the workflow.

The workflow execution unit 227 determines whether or not the operationto the agent 3 succeeded (Step D12). If it is determined that theoperation succeeded, it notifies the completion of the process (StepD14), and returns to Step D1, where it regains the monitoring state. Ifit is determined that the operation failed, the workflow execution unit227 notifies the failure (Step D13), and returns to Step D1, where itregains the monitoring state. The operation of monitoring the resourceinformation in Step D1 is conducted periodically and, if a plurality ofevents takes place simultaneously, the sequence of the process from StepD2 to Step D14 is executed for the plurality of events concurrently.

In the present embodiment, the resource providing server 2 collectsresource information 31 from the agents 3 based on the updating schedulestored in the schedule storage unit 225, and stores the same in theresource information storage unit 222. When the resource providingserver 2 receives a retrieval request from the resource user terminal 1,the resource providing server 2 forwards back the resource informationstored in the resource information storage unit 22 to the resource userterminal 1. Therefore, the resource user terminal 1 can quickly obtainthe retrieved resource information if compared with an arrangement wherethe agents 3 are accessed to acquire resource information each time aretrieval process takes place.

Since resource information can be acquired in a short time in thepresent embodiment after a retrieval process takes place, the state ofresources can be monitored with ease in an environment where resourcesare widely distributed. Additionally, since the retrieval process fromthe resource selection component 13 is executed at a high speed, theresource selection process is also executed at a high speed in theenvironment where resources are widely distributed. Further, since theretrieval process from the workflow management component 23 is executedat a high speed, the time length for generating a workflow is reducedand the workflow generation process is stabilized.

In the present embodiment, the static schedule generation unit 224selects the updating interval of the resource information of eachresource category and generates an updating schedule. Thus, it ispossible to realize an updating process of resource information for eachresource category based on the characteristics of resources of thecategory. Additionally, as the resource information storage unit 222stores the most recently updated resource information, it is possible toprovide the resource user terminal 1 with the most recently updatedresource information. Therefore, the resource user terminal 1 cangenerate an event according to the latest state of resources and henceautonomously deal with the event at a higher speed.

For accessing the agents 3 to acquire resource information and providethe same to a resource user terminal 1, upon generation of a retrievalprocessing, the time length needed for the resource user terminal 1 toacquire the resource information varies depending on the resourceinformation to be retrieved, if the time length for accessing the agents3 varies from agent to agent. On the other hand, in the presentembodiment, the resource information requested to be retrieved isprovided from the resource information storage unit 222, the range ofvariation in the time length required for the acquisition of resourceinformation among the agents 3 can be concealed, whereby is possible toprovide the resource user terminal 1 with resource information in astabilized retrieval time.

It is assumed here that an event (action) of adding a host takes place,for example. In such a case, if it takes a long time to retrieveresource information and the host adding process has not completed whenthe next event of adding another host takes place, the another hostadding process needs to be started in a duplicated process. For avoidingsuch a situation, it is necessary to check whether or not the currenthost adding process is still going when the next event of adding theanother host takes place. With the present embodiment, a process ofretrieving the resource information is completed in a stabilizedretrieval time so that such a checking operation is not required becausethe retrieval time is shorter than the cycle of event generation. Thus,since the present embodiment can provide resource information in astabilized retrieval time, it is possible to alleviate the load ofmanagement in various states that arise due to a prolonged resourceinformation retrieval time.

FIG. 9 shows the configuration of a resource management component 22 ain a resource management system according to a second embodiment of thepresent invention. The resource management component 22 a includes anevent management unit 228, a dynamic schedule generation unit 229, asystem state monitor unit 230, a cache monitor unit 231, a retrievalprocess monitor unit 232 and a trouble detection unit 233 in addition tothe units illustrated in FIG. 2. In the present embodiment, the dynamicschedule generation unit 229 dynamically modifies the updating schedulestored in the schedule storage unit 225.

The system state monitor unit 230 monitors the load information of thecomputer system that realizes the resource management component 22 a,and the traffic of the network. The system state monitor unit 230 issuesan event under predetermined conditions based on the load informationand the traffic. When the resource information stored in the resourceinformation storage unit 222 is updated by the resource informationupdate unit 223, the cache monitor unit 231 compares the resourceinformation before the update and the resource information after theupdate, and monitors whether or not a change takes place due to theupdate. Then, it issues an event that can be differentiated depending onwhether or not the change takes place.

The retrieval process monitor unit 232 monitors the retrieval processthat the retrieval process unit 221 receives. If the retrieval processunit 221 receives the retrieval process, the retrieval process monitorunit 232 issues an event that indicates the reception of the retrievalprocess. The trouble detection unit 233 monitors the network beingmanaged by the resource providing server 2 and, when a trouble takesplace in the network, the trouble detection unit 233 issues an eventthat indicates the occurrence of the trouble. In the present embodiment,the workflow execution unit 227 issues an event based on the workflow tobe executed when it executes the workflow.

The event management unit 228 monitors the events generated by theworkflow execution unit 227, the system state monitor unit 230, thecache monitor unit 231, the retrieval process monitor unit 232 and thetrouble detection unit 233. When, for instance, the workflow executionunit 227 issues an event indicating the execution of a workflow thatproduces a change in the state of a resource as a result of theexecution of the workflow, the event management unit 228 acquiresinformation relating to the changed resource from the workflow executionunit 227. Thereafter, the event management unit 228 notifies the dynamicschedule generation unit 229 of an event indicating the execution of theworkflow that involves a change in the state of the resource andinformation on the changed resource.

When, for instance, the system state monitor unit 230 issues an eventindicating that an increase of the load of the computer system takesplace, the event management unit 228 acquires information on the loadfrom the system state monitor unit 230 and notifies the dynamic schedulegeneration unit 229 of the fact that the event takes place and theacquired load information. When the cache monitor unit 231 issues anevent indicating that the resource information is not changed by theupdate, the event management unit 228 acquires information relating tothe unchanged resource information from the cache monitor unit 231 andnotifies the dynamic schedule generation unit 229 of the fact that theevent takes place and the information relating to the unchanged resourceinformation.

When, for instance, the retrieval process monitor unit 232 issues anevent indicating that a retrieval process takes place, the eventmanagement unit 228 acquires information relating to the retrievedresource information from the retrieval process monitor unit 232 andnotifies the dynamic schedule generation unit 229 of the fact that theevent takes place and the information relating to the retrieved resourceinformation. When the trouble detection unit 233 issues an eventindicating that a trouble takes place in the network, the eventmanagement unit 228 acquires information relating to the location of thetrouble that takes place from the cache monitor unit 231 and notifiesthe dynamic schedule generation unit 229 of the fact that the eventtakes place and the information relating to the location of the troublethat takes place.

Immediately after the start of operation of the resource managementsystem, the schedule storage unit 225 stores therein the updatingschedule generated by the static schedule generation unit 224. Thedynamic schedule generation unit 229 alters the updating schedule storedin the schedule storage unit 225 based on the notifications from theevent management unit 228. Alternatively, the dynamic schedulegeneration unit 229 regenerates an updating schedule and stores the samein the schedule storage unit 225.

FIG. 10 shows the operation of the cache updating schedule modifyingprocess in a flowchart. The event management unit 228 monitors thegeneration of an event (Step E1) and determines whether or not an eventtakes place (Step E2). If it is determined in Step E2 that no eventtakes place, the event management unit 228 returns to Step E1 and standsby there until an event takes place.

When it is determined in Step E2 that an event takes place, the eventmanagement unit 228 determines whether or not the generated eventinfluences the resource information updating schedule and also whetheror not the updating schedule requires adjustment (Step E3). If it isdetermined in Step E3 that the updating schedule does not require anyadjustment, the event management unit 228 returns to Step E1 and standsby there until an event takes place.

The event management unit 228 associates the events generated by theworkflow generation unit with the pieces of information indicatingwhether or not the state of resources is altered by the execution of aworkflow and stores them. The event management unit 228 determineswhether or not the updating schedule requires adjustment as a result ofthe generation of an event by referring to the pieces of information.If, for example, an event is notified by the workflow execution unit 227and the event indicates the execution of a workflow that alters thesetting of the server hosts and the network equipment, the eventmanagement unit 228 determines that the updating schedule requiresadjustment in Step E3.

If an event is notified by the system state monitor unit 230 and theevent indicates a rise of the load of the computer system, the eventmanagement unit 228 determines that the updating schedule requiresadjustment in Step E3. If an event is notified by the cache monitor unit231 and the event indicates that the resource information is not changedby an update, the event management unit 228 determines that the updatingschedule requires adjustment. If an event is notified by the retrievalprocess monitor unit 232 and the event indicates that a retrievalprocess takes place for the resource information, the event managementunit 228 determines that the updating schedule requires adjustment. Ifan event is notified by the trouble detection unit 233 and the eventindicates that a trouble takes place, the event management unit 228determines that the updating schedule requires adjustment.

When the event management unit 228 determines that the updating schedulerequires adjustment in Step E3, it notifies the dynamic schedulegeneration unit 229 of the fact that an event that influences theschedule takes place and the information acquired from the workflowexecution unit 227, the system state monitor unit 230, the cache monitorunit 231, the retrieval process monitor unit 232 or the troubledetection unit 232. The dynamic schedule generation unit 229 has aschedule alteration policy file that describes the rules for decidinghow to adjust the updating schedule in response to each event of whichit may be notified and executes a process of adjusting the updatingschedule in response to the event that takes place by referring to theschedule alteration policy file (Step E4).

Now, the adjustment of the updating schedule in Step E4 will bedescribed in detail below. FIG. 11 shows the configuration of a computersystem that is an object of management. The adjustment of the updatingschedule that the dynamic schedule generation unit 229 carries out willbe described by way of an example where a workflow of moving Host01 frompool server 50 to business AP cluster 60 is executed by referring toFIG. 11. The event management unit 228 receives a notification of anevent of moving Host01 to the business AP cluster 60 from the workflowexecution unit 227, and notifies the dynamic schedule generation unit229 of information relating to the generated event.

The dynamic schedule generation unit 229 has information with respect tothe configuration of the network system that is an object of monitoring,as information models such as CIM (common information model). As theworkflow is executed by referring to information relating to theconfiguration, the dynamic schedule generation unit 229 lists up thepieces of resource information for which the cache needs to be updatedquickly. In the example of FIG. 11, the dynamic schedule generation unit229 lists up the information on the assignment of the Host01, the IPaddress information of the Host01, the information on the setting of theL2 switch, the information on the setting of the FW, the information onthe application that operates on the Host01, the information on the backend (Host05) of the application and the information on the setting ofthe LB as pieces of resource information that need to be updatedquickly.

The schedule alteration policy file describes that the pieces ofresource information on alterations of settings need to be updatedquickly as the policy for modifying the updating schedule when any ofthe resource settings is altered. The dynamic schedule generation unit229 modifies the updating schedule stored in the schedule storage unit225 so as to update the pieces of resource information listed up asthose that need to be updated quickly at the time of the next polling bythe resource information update unit 223 by referring to the schedulealternation policy file. By doing so, the pieces of resource informationstored in the resource information storage unit 222 are updatedimmediately by the resource information update unit 229 so that the mostrecently updated pieces of information can be provided from the resourceinformation storage unit 222.

Additionally, if a server host is added or deleted, for example, as aresult of the execution of the workflow while the system is inoperation, the dynamic schedule generation unit 229 is notified ofinformation relating to the event for the same. The schedulemodification policy file describes that, when the number of resources isincreased or decreased, the updating schedule is to be regenerated so asto be adapted to the number of resources after the change. The dynamicschedule generation unit 229 determines the number of simultaneousaccesses of agents based on the number of resources after the change bymeans of an algorithm similar to that of the static schedule generationunit 224 (FIG. 3) and generates an updating schedule of each resource.As a result, the process of updating the resource information based onthe number of resources is executed.

The schedule alteration policy file describes to prolong or shorten theupdating the interval based on the load or the traffic as the policy tobe started when the load of the computer system or the traffic of thenetwork rises. When, for example, the system state monitor unit 230issues an event indicating that the CPU load exceeds 90%, the dynamicschedule generation unit 229 receives a notification of the event by wayof the event management unit 228. Then, the dynamic schedule generationunit 229 alters the polling interval of the resource information updateunit 223 from 1 second to 1.5 seconds, for example, to prolong theresource information updating interval.

When, for example, the system state monitor unit 230 issues an eventindicating that the network traffic is not higher than 5 kbps, thedynamic schedule generation unit 229 receives a notification of theevent by way of the event management unit 228. Then, the dynamicschedule generation unit 229 reduces the polling interval only once inthe updating interval of the resource information belonging to, forexample, the server host, so as to raise the frequency of updating theresource information. In this way, it is possible to execute a cacheupdating process so as to suppress any overload by changing the updatinginterval and adapting to the environment of the system that is changingon a real time basis.

The schedule alteration policy file describes to prolong the updatinginterval of the resource information stored in the resource informationstorage unit 222 as the policy to be started when the resourceinformation is not changed by an update of the resource information bythe resource information update unit 223. When the cache monitor unit231 issues an event indicating that the resource information is notchanged by an update, the dynamic schedule generation unit 229 receivesa notification of the event by way of the event management unit 228 andmodifies the updating schedule stored in the schedule storage unit 225so as to prolong the resource information updating interval from thecurrent updating interval.

For example, if the resource information of the Host02 in FIG. 11 is notchanged, the dynamic schedule generation unit 229 alters the resourceinformation updating interval of the Host02 from the initial value (3seconds) for the server hosts defined by the static schedule generationunit 224 to 4 seconds. Thereafter, an updating schedule is prepared forthe Host02 based on the altered updating interval, and the updatingschedule stored in the schedule storage unit 225 is modified. Thus, thefrequency of updating the resource information whose value is notchanged can be reduced by doing so.

The schedule alteration policy file describes to prolong the updatinginterval of the resource information stored in the resource informationstorage unit 222 as the policy to be started when the resourceinformation is not changed by an update of the resource information bythe resource information update unit 223. When the cache monitor unit231 issues an event indicating that the resource information is notchanged by an update, the dynamic schedule generation unit 229 receivesa notification of the event by way of the event management unit 228 andmodifies the updating schedule stored in the schedule storage unit 225so as to prolong the resource information updating interval from thecurrent updating interval.

The schedule alteration policy file describes to shorten the updatinginterval of the resource information to which a retrieval process takesplace as the policy to be started when a retrieval process takes place.When the retrieval process monitor unit 232 issues an event indicatingthat a retrieval process takes place, the dynamic schedule generationunit 229 receives a notification of the event by way of the eventmanagement unit 228 and modifies the updating schedule stored in theschedule storage unit 225 so as to shorten the resource informationupdating interval of the resource information to which the retrievalprocess takes place and those of the pieces of resource relating to thatresource information from the current updating interval.

For example, when a retrieval process takes place to the resourceinformation of the Host01, the dynamic schedule generation unit 229alters the updating interval of the resource information of the Host01from the initial value (5 seconds) for the server hosts to 4 seconds.Additionally, the updating interval of the resource information relatingto the Host01 are shortened from the current level. Thereafter, anupdating schedule is prepared for the Host01 and the related resourceinformation based on the altered updating interval, and the updatingschedule stored in the schedule storage unit 225 is modified. Thus, theupdating interval of the resource information in which users are highlyinterested are reduced and resource information that is retrievedfrequently is updated also frequently, whereby users can be providedwith the most recently updated resource information.

The schedule alteration policy file describes to intensively update theresource information relating the resource to which a trouble occurs asthe policy to be started when a trouble occurs. When the troubledetection unit 233 issues an event indicating that a trouble occurs, thedynamic schedule generation unit 229 receives a notification of theevent by way of the event management unit 228 and modifies the updatingschedule of the resource information relating to the resource to which atrouble occurs, whereby the resource information is updated immediately.

With this arrangement, it is possible to provide the most recentlyupdated resource information for the resource that need to be handledaccurately and quickly for the trouble.

In the present embodiment, the dynamic schedule generation unit 229dynamically changes the updating schedule stored in the schedule storageunit 225 based on the events being managed by the event management unit228, and the resource information update unit 223 updates pieces ofresource information based on the schedule that dynamically changes.With this arrangement, the present embodiment provides the advantage ofefficiently collecting resource information based on the natures ofresources and the state of the computer system for realizing theresource management component 22 a in addition to the advantages of thefirst embodiment.

FIG. 12 shows an agent in a resource management system according to athird embodiment. The overall configuration of the resource managementsystem of the present embodiment is similar to that of the first orsecond embodiments; however, at least some of the agents 3 have theconfiguration as shown in FIG. 12. In the present embodiment, either thestatic schedule generation unit 224 or the dynamic schedule generationunit 229 requests the agents 3 a to automatically transmit resourceinformation from the side of the agent 3.

Each of the agents 3 a includes a notification management unit 303 andan event management unit 304 in addition to the manager connection unit301 and the resource information acquisition unit 302. If the agent 3 areceives a request for transmission of resource information from theresource information update unit 223, the agent 3 a operates similarlyto the agents 3 of the first and second embodiments to acquire therequired resource information 31, and transmit the same to the resourceinformation update unit 223. The event management unit 304 manages theevents that are generated in the inside and at the outside of the agents3 a. The notification management unit 303 stores information onauthorization and non-authorization of automatic transmission ofresource information and the conditions of transmission of resourceinformation when automatic transmission is authorized.

The static schedule generation unit 224 or the dynamic schedulegeneration unit 229 transmits an automatic notification requestincluding information specifying the conditions of transmission ofresource information to the agent 3 a that is to automatically transmitresource information. Upon receiving the automatic notification requestfrom the static schedule generation unit 224 or the dynamic schedulegeneration unit 229, the notification management unit 303 of the agent 3a stores information that automatic transmission of resource informationis authorized and also the conditions of transmission of resourceinformation contained therein.

The static schedule generation unit 224 or the dynamic schedulegeneration unit 229 specifies transmission at predetermined timeinterval or transmission in response to a predetermined event ascondition of transmission of resource information. If, for instance,transmission resource information at a predetermined time interval isspecified as condition of transmission, the agent 3 a starts the processof acquiring resource information at the specified predetermined timeintervals and transmits the acquired resource information to theresource information update unit 223. If, on the other hand,transmission in response to a predetermined event is specified ascondition of transmission, the event management unit 304 starts theprocess of acquiring resource information at the timing of detection ofsuch a predetermined event and transmits the acquired resourceinformation to the resource information update unit 223.

FIG. 13 shows in a flowchart the procedure of registering an automatictransmission of resource information in the notification management unit303. While the static schedule generation unit 224 transmits anautomatic notification request for resource information in the followingdescription, a similar sequence of operation is executed if the dynamicschedule generation unit 229 transmits the automatic notificationrequest. When there is an agent to which automatic notification ofresource information is to be requested for generation of a staticschedule, the static schedule generation unit 224 (FIG. 2) transmits anautomatic notification request to the agent 3 a (Step F1).

For example, the static schedule generation unit 224 transmits anautomatic notification request to the agent 3 a that acquires resourceinformation on a resource that belongs to the category of networkequipment. At this step, information specifying the clock time forstarting the transmission and the interval of transmission of resourceinformation is contained in the automatic notification request as thecondition of transmission based on the generated static schedule (FIG.5) so that the resource information update unit 223 can update theresource information. Then, the agent 3 a receives the automaticnotification request at the manager connection section 301 (Step F2).The notification management unit 303 stores the condition oftransmission of resource information based on the received automaticnotification request (Step F3).

FIG. 14 shows in a flowchart the procedure of the resource informationnotifying process that an agent 3 a follows when transmitting resourceinformation at the specified time interval. The notification managementunit 303 stores therein the fact that automatic transmission isauthorized and the specified time interval of transmission of resourceinformation. The notification management unit 303 stands by until thetiming of the next transmission of resource information arises (StepG1). When the specified clock time arises for starting transmission ofresource information under the transmission conditions registered byfollowing the sequence of FIG. 13 or the specified time elapses sincethe last transmission of resource information, the notificationmanagement unit 303 starts the process for notification of resourceinformation and acquires resource information 31 by way of the resourceinformation acquisition unit 302.

The notification management unit 303 transmits the acquired resourceinformation 31 toward the resource information update unit 223 by way ofthe manager connection unit 301 (Step G3). The agent 3 a repeats StepsG1 through G3 and transmits resource information to the resourceinformation update unit 322 at the specified time interval. The resourceinformation update unit 223 updates the resource information stored inthe resource information storage unit 222 by the received resourceinformation.

FIG. 15 shows in a flowchart the procedure of the information notifyingprocess that an agent 3 a follows in response to a predetermined event.When there takes place an event such as a system error of the OS or anapplication error or an event indicating that the CPU load of the agent3 a exceeds the threshold value, the static schedule generation unit 224requests transmission of resource information to the agent 3 a. Theevent management unit 304 monitors events that can take placeirregularly and stands by until an event takes place (Step H1). When theevent management unit 304 detects an event that takes place, ittransmits a notification of the event to the notification managementunit 303.

The notification management unit 303 determines whether or not the eventthat takes place specifies that resource information is to betransmitted in response to the event under the transmission conditionsstored in the procedure illustrated in FIG. 13 (Step H2). When thenotification management unit 303 determines in Step H2 that it isspecified to transmit resource information in response to the generationof the event, the notification management unit 303 starts the process oftransmitting resource information and acquires the resource information31 to be transmitted by way of the resource information acquisition unit302 (Step H3). Thereafter, the notification management unit 303transmits the acquired resource information 31 to the resourceinformation update unit 223 by way of the manager connection unit 301(Step H4). When the notification management unit 303 determines in StepH2 that it is not specified to transmit resource information in responseto the generation of the event, the notification management unit 303returns to Step H1 and stands by until the next event takes place.

FIG. 16 shows in a flowchart the procedure of the process of releasingan automatic notification request. When the static schedule generationunit 224 releases the automatic notification from an agent 3 a, ittransmits an automatic notification release request (Step 11). Thenotification management unit 303 receives this automatic notificationrelease request by way of the management connection unit 301 (Step 12).Then, it finds out the information relating to the automaticnotification to be released from the stored settings for authenticationnotification and destroys the information (Step 14). Thereafter, theagent 3 a transmits resource information to the resource informationupdate unit 223 according to an agent access from the side of theresource management component 22.

It is assumed here that server host information, application informationand network information are to be handled by means of the resourcemanagement system 100 a of the present embodiment. The resourcemanagement component 22 requests the agent 3 a that acquires informationon the setting of the network equipment for automatic notification ofresource information, for example. The agent 3 a notifies the resourcemanagement component 22 of resource information at the time intervalspecified in the automatic notification request, at a time interval of 5seconds for instance. The resource management component 22 accesses theagent 3 a based on the schedule stored in the schedule storage unit 225for resource information other than information on the setting of thenetwork equipment.

In the present embodiment, the agent 3 a automatically transmitsresource information under the conditions specified by the resourcemanagement component 22. With this arrangement, the resource managementcomponent 22 can acquire resource information from the agent 3 a withoutexecuting the process of an agent access, and thus reduce the number ofagent accesses by the resource management component 22 and hence theprocessing load in addition to the advantages that the first embodimentprovides.

The setting of automatic notification of resource information can bearbitrarily defined and released by means of an automatic notificationrequest from the resource management component 22 in the presentembodiment. Additionally, the conditions of automatic notification ofresource information can be arbitrarily defined. With this arrangement,it is possible to realize an update notification process that satisfiesthe request of the resource management component 22. For instance, whenthe updating interval is altered by the dynamic schedule generation unit229, the resource management component 22 can update resourceinformation at the altered updating interval. Additionally, the agent 3a is adapted to notify the resource management component 22 of whattakes place non-periodically such as a situation where the load of CPUof the agent 3 a exceeds the threshold value and a situation where atrouble occurs. With this arrangement, the resource management component22 can acquire such information without periodically accessing theagent.

FIG. 17 sows the configuration of a computer for realizing the resourcemanagement component 22. The computer 220 includes an input unit 4, aresource information management program 5, a data processing unit 6, anoutput unit 7 and a memory unit 8. The resource information managementprogram 5 is read into the data processing unit 6 to control theoperation of the data processing unit 6 and realizes the retrievalprocessing unit 221, the resource information update unit 223, thestatic schedule generation unit 224, the agent connection managementunit 226, the workflow execution unit 227, the event management unit228, the dynamic schedule generation unit 229, the system state monitorunit 230, the cache monitor unit 231, the retrieval process monitor unit232 and the trouble detection unit 233. The storage unit 8 realizes theresource information storage unit 222 and the cache update schedulestorage unit 225. The resource management components 22 of the firstthrough third embodiments are realized by means of such a computer 220.

While the updating schedule of each resource generated by the staticschedule generation unit 224 is stored in the schedule storage unit 225upon starting to operate in the second embodiment, the present inventionis by no means limited thereto. For example, it is possible to allow theschedule storage unit 225 to store the updating schedule for updatingeach resource at the same updating interval by way of the input unit 4and then allow the dynamic schedule generation unit 229 to modify theupdating schedule.

FIGS. 18( a) to (d) illustrate a timetable for modifying the updatingschedule. Initially, the updating interval is defined to be 4 secondsfor each resource (FIG. 18( a)). The resource is updated every 4 secondfrom a given clock time t. When the resource information of host01,host02 and host03 is updated from the resource information stored in theresource information storage unit 222, the dynamic schedule generationunit 229 reduces the updating interval of the resource information ofthe host servers from 4 seconds to 3 seconds. When the resourceinformation of L2SW and L3SW is not altered from that stored in theresource information storage unit 222, the dynamic schedule generationunit 229 prolongs the updating interval of those network equipments from4 seconds to 5 seconds (FIG. 18B).

The resource information update unit 223 updates the resourceinformation of Host01, Host02 and Host03 at 7 seconds after a givenclock time t based on the altered updating schedule. When the resourceinformation of the server hosts is not altered as a result of theupdate, the resource information update unit 223 prolongs the updatinginterval of those server hosts from 3 seconds to 4 seconds (FIG. 18C).Subsequently, the resource information update unit 223 updates theresource information of L2SW and L3SW at 9 seconds after a given clocktime t. When the resource information of the network equipments is notaltered as a result of the update, the dynamic schedule generation unit229 prolongs the updating interval of those network equipments from 5seconds to 6 seconds (FIG. 18D). By doing so, it is possible to updatethe resource information of each resource at an updating interval suitedfor the state of the resource without preparing an updating schedule foreach resource.

Meanwhile, the updating interval of resource information may becomesexcessively long when the updating interval is prolonged gradually forthe resource information that has not been changed for a long period oftime. To prevent such a situation from taking place, the dynamicschedule generation unit 229 may define an upper limit value in advancefor the updating interval of each resource. The updating interval canfluctuate between two values when the updating interval is prolonged andshortened repeatedly. In such a case, the dynamic schedule generationunit 229 may select the average of the two values for the updatinginterval of the resource information. Then, it is possible to stabilizethe updating interval.

While the present invention is described above by way of preferredembodiments, the resource management system according to the presentinvention is by no means limited to the above-described embodiments,which may be modified and altered in various different ways withoutdeparting from the spirit and scope of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing the configuration of a resourcemanagement system according to a first embodiment of the presentinvention;

FIG. 2 is a block diagram showing the detailed configuration of theresource management component 22 and agents 3;

FIG. 3 is a flowchart showing the algorithm of static schedulegeneration by the static schematic generation unit 224;

FIG. 4 is a concrete example of the resource profile;

FIG. 5 is a timetable showing a concrete example of the static schedulegenerated by the static schedule generation unit 224;

FIG. 6 is a flowchart showing the procedure of operation in the cacheupdating process;

FIG. 7 is a flowchart showing the procedure of operation in the resourceinformation retrieval requesting process;

FIG. 8 is a flowchart showing the procedure of operation in the resourcemanagement system;

FIG. 9 is a block diagram sowing the configuration of the resourcemanagement component 22 in a resource management system according to asecond embodiment of the present invention;

FIG. 10 is a flowchart showing the procedure operation in the cacheupdating schedule modifying process;

FIG. 11 is a block diagram showing a computer system that is the objectof management;

FIG. 12 is a block diagram showing the configuration of an agent in aresource management system according to a second embodiment of thepresent invention;

FIG. 13 is a flowchart showing the procedure of operation in the processof registering a schedule in the notification management unit 303;

FIG. 14 is a flowchart showing the procedure of operation in theresource information notifying process;

FIG. 15 is a flowchart showing the procedure of operation in theinformation notifying process upon starting of an event;

FIG. 16 is a flowchart showing the procedure of operation in the processof releasing an automatic notification request;

FIG. 17 is a block diagram showing the configuration of a computer forrealizing the resource management component 22; and

FIGS. 18( a) to (d) are timetables for showing modification of theupdating schedule.

1-21. (canceled)
 22. A resource management system comprising a resourceinformation providing server for providing resource information relatinga plurality of resources connected to a network in response to a requestfrom a resource user, wherein: the resource information providing serverincludes: a resource information storage unit storing therein resourceinformation; a schedule storage unit storing therein an updatingschedule of the resource information stored in the resource informationstorage unit; and a resource information update unit for acquiring theresource information based on the schedule stored in the schedulestorage unit; and updating the resource information stored in theresource information storage unit by the acquired resource information;and the schedule storage unit stores therein at least an updatingschedule having an updating interval defined for each resource for whichresource information is to be acquired.
 23. The resource managementsystem according to claim 22, wherein the different types of resourceshave different updating time intervals.
 24. The resource managementsystem according to claim 22, wherein the resource information providingserver further includes a static schedule generation unit for generatingthe updating schedule generation unit for generating the updatingschedule based on to at least one of the pieces of the informationincluding the performance of the resource information providing server,an expected frequency of updating resource information, an expectedfrequency of request for resource information from resource users, anupdating time length expected to required to update each piece ofresource information and a number of resources, and storing thegenerated updating schedule in the schedule storage unit.
 25. Theresource management system according to claim 22, wherein the resourceinformation providing serve further includes a dynamic schedulegeneration unit for dynamically modifying the updating schedule storedin the schedule storage unit based on at least one of a state of theresources, a state of the resource information providing server and astate of the communication line.
 26. The resource management systemaccording to claim 25, wherein the dynamic schedule generation unitmodifies the updating schedule based on an increase or decrease of thenumber of resources.
 27. The resource management system according toclaim 25, wherein the dynamic schedule generation unit shortens theupdating interval of the resource information for which the request isproduced when a request for resource information is produced by aresource user.
 28. The resource management system according to claim 25,wherein the dynamic schedule generation unit shortens the updatinginterval of the resource information relating to a trouble when thetrouble arises to any of the resources or a communication line.
 29. Theresource management system according to claim 24, wherein the dynamicschedule generation unit shortens the updating interval of the resourceinformation of an altered resource when the configuration of a resourceis altered.
 30. The resource management system according to claim 25,wherein the dynamic schedule generation unit prolongs the updatinginterval of the resource information that has not altered by pastupdates of resource information.
 31. The resource management systemaccording to claim 25, wherein the dynamic schedule generating unitprolongs the updating interval of resource information as a whole when aload of the resource information providing server or the communicationline rises.
 32. The resource management system according to claim 22,characterized by further comprising an agent for collecting resourceinformation from the resources, the agent being adapted to transmitresource information to the resource information update unit.
 33. Theresource management system according to claim 32, wherein the agentregisters notification conditions and an automatic notification requestthat specifies resource information in advance and, when notificationconditions specified by the automatic notification request arise, theagent transmits the resource information specified by the automaticnotification request to the resource information update unit.
 34. Theresource management system according to claim 22, wherein the updatingschedule specifies the resource information to be acquired at each ofthe pollings that the resource information update unit carries out at apredetermined time interval.
 35. The resource management systemaccording to claim 34, wherein the upper limit of the resourceinformation to be acquired at each polling is specified based on thememory capacity of the resource information providing server.
 36. Aresource management system comprising a resource information providingserver for providing resource information relating to a plurality ofresources connected to a network in response to a request from aresource user, characterized in that: the resource information providingserver includes: a resource information storage unit storing resourceinformation; a schedule storage unit storing an updating schedule of theresource information stored in the resource information storage unit; aresource information update unit for acquiring the resource informationaccording to the schedule stored in the schedule storage unit andupdating the resource information stored in the resource informationstorage unit by the acquired resource information; and a dynamicschedule generation unit for dynamically modifying the updating schedulestored in the schedule storage unit based on at least one of a state ofthe resources, a state of the resource information providing server anda state of the communication line.
 37. A method for providing resourceinformation by means of a resource information providing server forproviding resource information relating to a plurality of resourcesconnected to a network, in response to a request from a resource user,the method comprising: storing in a schedule storage unit an updatingschedule defining an updating timing of resource information andincluding an updating interval selected at least for each resource forwhich resource information is to be acquired; acquiring resourceinformation based on the updating schedule stored in the schedulestorage unit and storing the acquired resource information in a resourceinformation storage unit; and providing the resource information storedin the resource information storage unit in response to a request from aresource information user.
 38. The resource management method accordingto claim 37, wherein the different types of resources have differentupdating time intervals.
 39. A method for providing resource informationby means of a resource information providing server for providingresource information relating to a plurality of resources connected to anetwork in response to a request from a resource user, the methodcomprising: storing an updating schedule defining the updating timing ofresource information in a schedule storage unit; acquiring resourceinformation according to the updating schedule stored in the schedulestorage unit and storing the acquired resource information in a resourceinformation storage unit; dynamically modifying the updating schedulestored in the schedule storage unit based on at least one of a state ofthe resources, a state of the resource information providing server anda state of a communication line; and providing the resource informationstored in the resource information storage unit in response from aresource information user.
 40. A computer readable program for aresource information providing server for providing resource informationrelating to a plurality of resource connected to a network, in responseto a request from a resource user, the program defining: storing in aschedule storage unit an updating schedule defining an updating timingof resource information and including an updating interval selected atleast for each resource for which resource information is to beacquired; acquiring resource information based on the updating schedulestored in the schedule storage unit and storing the acquired resourceinformation in a resource information storage unit; and providing theresource information stored in the resource information storage unit inresponse to a request from a resource information user.
 41. The programaccording to claim 40, wherein the different types of resources havedifferent updating time intervals.
 42. A computer readable program for aresource information providing server for providing resource informationrelating to a plurality of resources connected to a network, in responseto a request form a resource user, the program defining: storing anupdating schedule defining the updating time of resource information ina schedule storage unit; acquiring resource information according to theupdating schedule stored in the schedule storage unit and storing theacquired resource information in a resource information storage unit;dynamically modifying the updating schedule stored in the schedulestorage unit based on at least one of a state of the resources, a stateof the resource information providing server and a state ofcommunication line; and providing the resource information stored in theresource information storage unit in response to a request from aresource information user.